home *** CD-ROM | disk | FTP | other *** search
-
- If you are having problems getting Vertex to run on your system, please
- read below:
-
- MULTITASKING
-
- If you are having problems with multitasking on your Amiga while Vertex
- is running, remember to either choose the menu option MISC-SLEEP, or
- press the HELP key.
-
- INIT ERRORS:
-
- 8: There seems to be some minor memory problems when using Vertex on
- systems with "too-much" memory. If you have over 8 megs of memory,
- try filling some up with another application before running Vertex.
-
- Version 1.15 and above fixes this problem by limiting the
- number of vertices, edges and faces to 32760. Future versions
- will contain a "large" memory model so that vertices edges
- and faces can number up to about 1,000,000,000. I hope that
- will be enough!
-
- Version 1.21 and up now offer 64000 vertices as a limit. I was
- limited to this number by other software which limits objects to
- have approximately 64000 vertices. If this is a major problem, let
- me know and I'll see what I can do about it.
-
- I have successfully used this scheme in tests on an Amiga 3000
- with over 8 megs of ram. If anyone has further problems with this,
- please let me know.
-
- RUN TIME ERRORS:
-
-
- I have tried to make many of the functions "stable" by first checking
- to see if there is enough memory available. It is kind of difficult
- for me to fully test these types of things, since I only have a 1 meg
- machine. Be leary of error 8, which is the out of internal memory
- error. When this happens, you are trying to operate on too many
- vertices at once. Let me know when you run into this error, and I
- should ba able to alter the code a bit to fit any special
- circumstance.
-
-
- GURUS:
-
- Again, if you have too much memory, Vertex may try to allocate more
- than 65000 vertices. This may run into problems in the edge list.
- If this is a problem, then turn the UNDO option to ON, and
- everything should be better.
-
- UNKNOWN RUN TIME ERRORS:
-
- Please let me know when you run into these errors. Include a brief
- description of your system set-up, and what you did before the
- error occured.
-
- If the UNKNOWN ERROR requestor will not go away, you may
- have to re-boot the machine. When errors occur, the system
- will abort any function and try to re-draw the screen. If the
- error occurred during a screen re-draw, then an infinite loop
- of errors will continuously appear.
-
- DRAWING:
-
- Be leary of using perspective mode when zoomed in on large
- objects. The system may lock up due to an unknown error. I'm in
- the process of re-writing the drawing routines so this kind of
- thing does not happen.
-
- GURUS WHILE READING:
-
- I've tried to make the file reading routines as "dummy proof"
- as possible. If you try and load a file, and Vertex does not
- know what it is, it will pup-up a menu and ask you if it is a
- Wavefront file. If it is, then select the menu item
- "Wavefront". If it is not a Wavefront file, then move off the
- menu to abort the read. If you don't you run the risk of
- crashing the system!
-
- Wavefront reading has been changed to make use of the ever present
- .obj on the end of Wavefront files. This is a last resort test, so
- if you have objects created with other software which end with
- .obj in their file name, they should still read correctly.
-
- -- Alex Deburie
-
-
-
-